fix: restore node shebang in published bin scripts#674
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The shebang in @perstack/base and @perstack/create-expert-skill was changed from `#!/usr/bin/env node` to `#!/usr/bin/env bun` during the Bun toolchain migration (#599). This breaks execution in environments where only Node.js is available (e.g. job executor containers), causing `/usr/bin/env: 'bun': No such file or directory`. These scripts use no bun-specific APIs and run fine under Node.js. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
#!/usr/bin/env nodeshebang in@perstack/baseand@perstack/create-expert-skillbin scripts#!/usr/bin/env bunduring the Bun toolchain migration (chore: migrate toolchain to Bun #599), but the scripts use no bun-specific APIsProblem
Job executor containers have only Node.js installed. When
@perstack/baseis resolved via npx (version-pinned experts), the#!/usr/bin/env bunshebang causes immediate failure:This has been breaking nearly all jobs since 2/25.
Test plan
#!/usr/bin/env nodein dist🤖 Generated with Claude Code